Created new 'estate' module.
Added base model 'estate.property' with fields mentioned in exercise.
Set up module structure.
Set 'name' and 'expected_price' as required fields.

This commit introduces the initial version of the estate module as part of the Odoo 18 developer tutorial. The module includes basic models, access rights, security rules, and simple form and tree views for managing real estate properties.
The purpose of this change is to set up a foundational structure for the module. It follows the official tutorial steps to demonstrate Odoo’s ORM, security mechanisms, and view definitions. Adding proper access control ensures that only authorized users can interact with the module. The initial UI provides the groundwork for extending functionality later.
This is part of a learning exercise to understand Odoo’s server framework and how to implement a feature-rich module following best practices.

-Created new models for property offers,tags and types.
-Defined relation between these data models for accessing data across the model.
-Created new views for property types,property tags.
-Defined action on button click , created computed fields .

Added SQL constraints to ensure:
Property expected price is strictly positive,
Property selling price is positive,
Offer price is strictly positive,
Property tag name and property type name are unique,
,

Added Python constraint to prevent selling price from being set below 90% of expected price,

Changes in UI:
Added inline list view for properties on property type form,
Used statusbar widget for property state display,
Defined default ordering for models and enabled manual ordering for property types via sequence field,
Applied widget options to restrict creation/editing of property types from property form

Added model and view inheritance for extending existing functionality.,
Implemented interaction with external modules using dependencies.,
Updated estate module to demonstrate cross-module field access and method calls.

- Cleaned up code to meet linting and CI style standards.

Implemented cross-module field access and method calls to demonstrate interaction with other modules.,
Cleaned codebase to fix linter errors and improve readability.

Added demo data and security data to the estate module.,
Implemented record rules and access rights to restrict data access based on user groups.,
Updated manifest.py to load new data files.

-Created a PDF report for estate properties listing all property offers using
QWeb templates and report actions.
-Extended the report in estate_account to include invoice details for sold
properties.
-Organized templates and report actions within their respective modules.
-Updated manifest files to register new reports.
-Enhances reporting by allowing users to generate comprehensive property and
financial documents from the UI.

Introduced new unit tests in the estate module covering key business processes:
Prevent offer creation on sold properties.,
Disallow marking properties as sold without an accepted offer.,
Ensure garden area and orientation fields reset appropriately when garden is unchecked.
These tests improve the reliability and maintainability of the estate workflow.